Before You Create Work Orders
Work orders rely on many different lookup tables and numbering masks to be defined beforehand. To adequately define work orders and their tasks, the following preparation is recommended:
For administrators:
- Define a lookup list of Work Order Types in tables. For example, AssetWise object creation, review, approve, change processing, and implementation.
- An optional Work Order Priority lookup list in the tables.
- Optional user-defined attributes in the tables to record additional data to support the enterprise business processes.
- A generic work order number mask in System AdminSystem DefaultsIdentification tables for ad-hoc work orders not copied from predefined templates.
- Task level Skills lookup table in tables.
- If you want users to create work orders from a template, you must create a work order template under a work order class, and the Status of the template must be Approved.
For users:
Note: If skills are defined
and used for a task, then all persons involved in receiving tasks must be
allocated the applicable skills, sinceAssetWise will only
allow persons with the correct skills to be assigned to a specific task. Tasks
can be defined with no skills defined. In this case any person can be allocated
the task.
See Maintaining List Values for details on Maintain List Values tables. If a system generated physical item number is required an appropriate numbering mask must be defined in the System Defaults.